I've been looking into this without any luck so far, mostly because I'm cheap and won't pay for IPB. Hard to test without it. However I just came across a "publicly accessible" version tonight so work can begin!

From initial inspection, "oh boy this is gonna get messy". Can't find any references to the API.

Can I convince you to use IPBoard 3?

I contacted Invisionpower regarding the API, they have no plans on implementing it right now. Which means we'd need to look at migrating group management to LDAP so that IPB4 can use it. That's a long way away.



Is it adding groups to every other service but ipboard?

It is entirely possible for you to be able to set it up yourself. As long has you are willing to google and figure out any problems you come across yourself. Many people just skip the googling step though heh.

Can you verify the following for me:

• You copied the aa folder to the interface/board/modules/ directory in IPBoard
• You updated IPBOARD_ENDPOINT in settings.py to point at the interface location (yourdomain.com/path/to/interface)
• You generated an API key and updated IPBOARD_APIKEY in settings.py with it

Updated the code base today. Hidden groups, a fix for TS3, and forum avatars. Read more about it and how to perform the update here.

No. The goal behind this change was to restrict the groups available to members to apply to on the website, meaning this group's membership can only be managed from the admin console.

I wrote a quick tool to link Alliance Auth ( https://forums.eveonline.com/default.aspx?g=posts&t=383030&find=unread ) API keys to the SeAT ( https://forums.eveonline.com/default.aspx?g=posts&t=336800 ) API keys. Might be useful to others.

https://github.com/awerries/allianceauth_to_seat

Yes I've used that before. You need to enter the API username and password generated by SeAT into that last line.

Within SeAT go to Configuration -> API Applications, add a new application (make sure the source IP is correct, 127.0.0.1 if on the same machine), and put the credentials it generates into conf.json. Ensure the MySQL tables and username/passwords are also correct.

That's really the cleanest way of doing it. You could in theory simply add another alias and directory to your allianceauth apache configuration, but I've had mixed results doing that.

So new problem to troubleshoot.

Finally getting ready to make everyone move to mumble. I noticed accounts are being created just fine, and when I check the DB, and look under murmur_group_members people are being assigned to the appropriate groups.

Mumble on the other hand doesn't seem to know people are in these groups unless I assign manually. Meaning, they won't be allowed access to channels that they should be as "members" until I manually add them to the members list.

So basically their accounts are being created, the db seems to know they are members, and mumble knows they are a registered user, but mumble doesn't seem to accept them as members.

Seems odd, open to any thoughts?

Try this:

python manage.py shell
from celerytask.tasks import run_databaseUpdate
run_databaseUpdate()

If that hangs, you'll have to restart the server. But at least I'll know it's not a fluke. I've had another guy reporting sync group issues.

They should not need to be sudo'd.

The issues you're experiencing, groups not updating on IPBoard, is very likely rooted in the run_databaseUpdate celery task hanging for some users - if you're affected, group updates will not occur. Watch this issue for updates.

Haven't had much time to debug because it's exam season. Couple more days till they're over.